Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

back

Account management

Branding inheritance

search

Branding inheritance

Branding inheritance

By default, every account that you on-board automatically inherits all branding and SMS gateway customizations that you apply to your virtual server.

In the following illustration, all child accounts in Tier 2 inherit the branding and customization settings configured by the parent account. If VSP-1 modifies the branding for a customization configuration in its virtual server, all of its child accounts in Tier 3 inherit the new branding and customizations.

When VSP-1 adds VSP-2 to its accounts, it can disable the ability for VSP-2 to modify branding and customization. In that case, VSP-2 and all of its child accounts in Tier 4 inherit branding and customization from VSP-1.

Similarly, VSP-3 inherits the branding and customization configuration from the parent account. If VSP-3 makes no changes, all of its child accounts in Tier 3 inherit the branding and customization configuration from the parent account .

SUB-1 can modify the branding and configuration that it inherited from VSP-3 to reflect its requirements.

A change at any time to the branding and customization configuration for VSP-3 is inherited only by its child accounts that have not applied their own customizations.

alt_text

Inherit or customize branding

Each of your accounts has its own virtual server that can be configured to override the inherited branding customizations. This is beneficial if your client requires their own brand or, as a virtual service provider, wants to resell your service under their brand.

If an account applies a customization to their virtual server, that virtual server no longer inherits any new customizations that you apply to your virtual server.

When branding is inherited, only the product name and the organization name can be customized.

alt_text

When branding is not inherited, the appearance and branding of the STA Token Management console, self-service, and enrollment web pages can be customized for colors, fonts, logos, titles, labels, and product name.

alt_text

  1. On the STA Token Management console, select Comms > Custom Branding.

  2. Select Set Customization Inherit.

    alt_text

  3. The virtual server can either inherit or customize the branding:

    • To inherit branding, select the Use Customizations Inherit check box.

    • To customize branding and override the inheritance, clear the Use Customizations Inherit check box.

      If the Use Customizations Inherit check box is subsequently selected, the virtual server inherits the system defaults and not the defaults from the service provider.

  4. Select Apply.

Preventing branding overrides

To prevent your child account accounts from overriding the inherited or custom branding that you apply to their virtual server, do one of the following:

  • Do not create an operator to be used by your client to log in to the STA consoles for their virtual server. If they cannot log in, they cannot make changes.

  • To allow your client to log in to the STA consoles for their virtual server, but not to modify customizations:

    • Do not use the Create Operator function on the ON-BOARDING tab to add your client as an operator, as this gives them the right to make modifications.

    • Instead, create a role that denies access to the Branding module. (To prevent changes to SMS gateways, email servers, and message contents, ensure that the role denies access to the Communications module.)

    • Add the client as a user, provision a token, promote the user to operator, and then assign the role with restricted permissions.

Custom URLs

The appearance and branding of the STA consoles, self-service pages, enrollment pages, and user portal can be customized for colors, fonts, logos, and titles.

The virtual server generates a unique URL for each customized page. Each virtual server must use their own unique URLS.

  • Operator logon page: The URL where operators log on to the STA consoles is displayed on the STA Token Management console in Comms > Custom Branding.

  • Self-service site: The self-service URL is displayed on the STA Token Management console in Self-Service > Configuring Self-Service > Self-Service Policy.

  • Enrollment pages: Enrollment page URLs are generated for each user that is part of a provisioning task. URLs are included in the notification email message to the user. The enrollment page URL is displayed on the STA Token Management console in Policy > Automation Policies > Self-Enrollment Policy.

  • User portal: The URL for the user portal is displayed on the STA Access Management console in Applications > User Portal.

Operators can also log on to the STA consoles at the default logon page (http://serviceURL/console), which uses the default STA branding.

You can also customize the information on the STA Token Management console, in Virtual Servers > Snapshot > References. The references include links to downloads, documentation, and terms of use.